﻿<?xml version="1.0" encoding="utf-8"?>
<!--Code Generated Analysis XML-->
<ULA>
  <Configuration>
    <Version>1.0.0</Version>
    <Product>SharePoint Server</Product>
    <Analysis>
      <Category>User Profile sync</Category>
      <XMLDescription>User Profile sync</XMLDescription>
    </Analysis>
  </Configuration>
  <ULAQuery>
    <Query>
	<ID>ac06bd95-afd6-41ca-bf9d-b4d7bff74cdf</ID>
	<Title>Unknown SQL exceptions - Event 5586 </Title>
	<Parameters>
		<EventID>5586</EventID>
		<Message>http://technet.microsoft.com/en-us/library/ee513056</Message>
		<SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '5586'</SQLQuery>
		<RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '5586'</RelevantLogCollection>
		<Symptom>The following symptom might appear:

This event appears in the event log: Event ID: 5586 Description: Database full error on SQL Server instance [instance name] in database [database name]. Additional error information from SQL Server is included below. [SQL error message].</Symptom>
		<Description>Microsoft SharePoint Foundation uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Web site. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server 2008. 

Microsoft SharePoint Foundation uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name or password (domain name and password), or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.</Description>
		<Cause>One or more of the following might be the cause:

Insufficient SQL Server database permissions

SQL Server database is full

Incorrect MDAC version

SQL Server database not found

Incorrect version of SQL Server

SQL Server collation is not supported

Database is read-only

The service account is not set up properly in SharePoint Foundation.</Cause>
		<Articles>http://technet.microsoft.com/en-us/library/ee513056</Articles>
	</Parameters>
</Query>
    <Query>
      <ID>15583495-e09b-4566-b592-96393e76f11f</ID>
      <Title>Insufficient SQL Server database permissions - Event 5214</Title>
      <Parameters>
        <EventID>5214</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513067</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '5214'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '5214'</RelevantLogCollection>
        <Symptom>The following symptom might appear:

This event appears in the event log: Event ID: 5214 Insufficient SQL database permissions for user '[username]' in database [database name] on SQL Server instance [instance name]. Additional error information from SQL Server is included below.</Symptom>
        <Description>Microsoft SharePoint Foundation uses Microsoft SQL Server 2008 databases to store most of the content for the Web site and configuration settings. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server.

SharePoint Foundation uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name and password (domain name and password) or a predefined system account, such as Local System or Network Service. This error occurs when the service account specified in SharePoint Foundation has not been granted sufficient permissions in the SQL Server database.</Description>
        <Cause>One or more of the following might be the cause:

The service account to which SharePoint Foundation is set does not have sufficient permissions to the database to which it is trying to connect.

The service account is not set up properly in SharePoint Foundation.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513067</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>90c5e41e-6c79-49c8-a0fa-1209fac8a723</ID>
      <Title>Content database is Read-Only - Event 4971 </Title>
      <Parameters>
        <EventID>4971 </EventID>
        <Message>http://technet.microsoft.com/en-us/library/ff182793</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '4971'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '4971'</RelevantLogCollection>
        <Symptom>One or more of the following symptoms might appear:

Users cannot add or update content in SharePoint Foundation 2010 sites.


The following event appears in the event log: Event ID: 4971 Description: Cannot update database on SQL Server instance '[instance name]'. Database is read/only. Additional error information from SQL Server is included below. [additional information]</Symptom>
        <Description>Microsoft SharePoint Foundation 2010 stores most of the content of the Web application — including site collections, sites, lists, documents, and permissions — in content databases. A single Web application can be associated with one or many content databases.</Description>
        <Cause>SQL Server provides the option of setting a database to read-only mode, in which data can be read from the database but data cannot be added, changed, or removed. If a content database is in read-only mode, you might observe the symptoms described.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ff182793</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>0d14f18e-4068-4eb2-8b76-ca3f4273a07d</ID>
      <Title>Database could not be accessed - Event 3760</Title>
      <Parameters>
        <EventID>3760</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513043</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3760'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3760'</RelevantLogCollection>
        <Symptom>The following symptoms might appear:

Content in the database is not available and attempts to access the database generate errors.


This event appears in the event log: Event ID: 3760 Description: SQL Database '[database name]' on SQL Server instance '[instance name]' not found. Additional error information from SQL Server is included below. [error information]</Symptom>
        <Description>Microsoft SharePoint Foundation 2010 uses Microsoft SQL Server 2008 databases to store most of the content for the Web site and configuration settings. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server.
SharePoint Foundation 2010 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific domain name/user name and password, or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.</Description>
        <Cause>One or more of the following might cause this:.

The SQL Server user login failed.


The database has been deleted or renamed.


The database is currently unavailable because it is in an offline or loading state.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513043</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>541f0ae9-ba5d-4829-b510-775b4bd5c81e</ID>
      <Title>SQL Server database is full - Event 3758</Title>
      <Parameters>
        <EventID>3758</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513057</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3758'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3758'</RelevantLogCollection>
        <Symptom>The following symptom might appear:

Users cannot add or update any content in SharePoint Foundation.

Administrators cannot update any SharePoint Foundation settings.

This event appears in the event log: Event ID: 3758 Description: Database full error on SQL Server instance [instance name] in database [database name]. Additional error information from SQL Server is included below. [SQL error message]</Symptom>
        <Description>Microsoft SharePoint Foundation uses Microsoft SQL Server 2008 databases to store most of the content for SharePoint Foundation Web site and configuration settings, and uses a service account to communicate with the database on behalf of a user request. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases. This error indicates that the database has reached the size of its maximum size setting.</Description>
        <Cause>The database has reached its maximum size.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513057</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>e5f4c99e-3ee1-4f98-817e-fb08c5cfaf75</ID>
      <Title>Cannot connect to SQL Server - Event 3355</Title>
      <Parameters>
        <EventID>3353 </EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513066</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3353'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3353'</RelevantLogCollection>
        <Symptom>One or more of the following symptoms might appear:

Attempts to communicate with SQL Server fail and no content from databases hosted on the SQL Server can be accessed.


This event appears in the event log: Event ID: 3355 Cannot connect to SQL Server. [Server Name] not found. Additional error information from SQL Server is included below.</Symptom>
        <Description>Microsoft SharePoint Foundation 2010 uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Microsoft SharePoint Foundation Web site. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server. 

SharePoint Foundation 2010 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name or password (domain name and password), or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.

This error indicates that Microsoft SharePoint Foundation could not connect to the SQL Server database.</Description>
        <Cause>One or more of the following might be the cause:

The SQL Server might be offline.

The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.

A firewall that runs on either the local server or on SQL Server might be blocking network communications.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513066</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>1f5fa1c2-5878-460c-b961-1c1d3dafa9fe</ID>
      <Title>SQL Server database login failed - Event 3351</Title>
      <Parameters>
        <EventID>3351</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513059</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3351'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '3351'</RelevantLogCollection>
        <Symptom>The following symptom might appear:

This event appears in the event log: Event ID: 3351 Description: SQL database login failed. Additional error information from SQL Server is included below.</Symptom>
        <Description>Microsoft SharePoint Foundation uses Microsoft SQL Server 2008 databases to store most of the content for SharePoint Foundation Web sites and configuration settings, and uses a service account to communicate with the database on behalf of a user request. Note that a Web application might be associated with one or many databases. This error — SQL Server database login failed — means that SharePoint Foundation cannot log on to SQL Server 2008 by using the specified service account user name and password.</Description>
        <Cause>The user name or password for the Microsoft SharePoint Foundation service account was invalid before the session or became invalid during the session.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513059</Articles>
      </Parameters>
    </Query>
  </ULAQuery>
</ULA>